Add new sampling method to the downsample API #5563
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
In elastic/elasticsearch#136813 we introduce one more configuration option in the downsample API that allows a user to choose the sampling method between:
aggregate: when supported, this will downsample a metric by summarising its values in a aggregate document. This remains the defaultlast_value: this will keep the last value and discard the rest.The issue here is that the sampling method will be introduced in the data stream lifecycle in a different way, see elastic/elasticsearch#137023:
In the elasticsearch specification we used the same type to capture the
fixed_intervalin both, but now we see that these have diverged, so we need to split them into two types in order to preserve correctness.This is an alternative to #5496.